Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07841b4bd3af87a302b80303857e377caa8177080eaccdb13889368893f82ca1

Tx prefix hash: 1fc498b3a448ae5f6d2799b8972e7801a11d9a4d51af8e8e59aba73be80acb22
Tx public key: d3f62e82bafe9a59eacb1ddf6d7da85ec415ff1587a6fafe492b3ca458e867cb
Timestamp: 1723004478 Timestamp [UCT]: 2024-08-07 04:21:18 Age [y:d:h:m:s]: 00:318:07:38:57
Block: 1082464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227274 RingCT/type: yes/0
Extra: 01d3f62e82bafe9a59eacb1ddf6d7da85ec415ff1587a6fafe492b3ca458e867cb02110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48c5035ec065cd1e79b9d1af01d4c73628ecdec8dbc57c033d1a60ade60d5c0c 0.600000000000 1556291 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": 1082474, "vin": [ { "gen": { "height": 1082464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48c5035ec065cd1e79b9d1af01d4c73628ecdec8dbc57c033d1a60ade60d5c0c" } } ], "extra": [ 1, 211, 246, 46, 130, 186, 254, 154, 89, 234, 203, 29, 223, 109, 125, 168, 94, 196, 21, 255, 21, 135, 166, 250, 254, 73, 43, 60, 164, 88, 232, 103, 203, 2, 17, 0, 0, 0, 16, 145, 225, 60, 4, 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