Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 5c03bf04f79ce4608305effe0f0998578665e50295890cce0fafd9e98803366f

Tx prefix hash: 2046f1cc8eb9c12c12b722ccd0bec59a2716990e9c8a47ca9afd6fab8b1de898
Tx public key: 81cd797889eac3c9d4a66b7898f88070d2f6f121324a7409ae0f1374f9eaa4b1
Timestamp: 1722835589 Timestamp [UCT]: 2024-08-05 05:26:29 Age [y:d:h:m:s]: 00:248:17:32:53
Block: 1081056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177670 RingCT/type: yes/0
Extra: 0181cd797889eac3c9d4a66b7898f88070d2f6f121324a7409ae0f1374f9eaa4b1021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 845d3a6d7b76420d356be5633322cc5dd545fb07515a9c46612049769f081d5b 0.600000000000 1554653 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1081066, "vin": [ { "gen": { "height": 1081056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "845d3a6d7b76420d356be5633322cc5dd545fb07515a9c46612049769f081d5b" } } ], "extra": [ 1, 129, 205, 121, 120, 137, 234, 195, 201, 212, 166, 107, 120, 152, 248, 128, 112, 210, 246, 241, 33, 50, 74, 116, 9, 174, 15, 19, 116, 249, 234, 164, 177, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8