Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b29a1561e4186542b60b28c7790fd007eb77ed27e5d67f4d6da52ef7bf210a1

Tx prefix hash: e2ac0342042610fc515af8cc30f937343f262601e2d28c94343a8fdee8eed969
Tx public key: fd3230c5e7d927da7e483519f1a3db558eec62e7d4847b526cfbc67789ef0d3e
Timestamp: 1722412600 Timestamp [UCT]: 2024-07-31 07:56:40 Age [y:d:h:m:s]: 00:314:01:29:47
Block: 1077554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224421 RingCT/type: yes/0
Extra: 01fd3230c5e7d927da7e483519f1a3db558eec62e7d4847b526cfbc67789ef0d3e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f03e4e2ba00f2f3d1a94aff3633261538f4d8dfc39a01145c89bcecf006552a 0.600000000000 1550105 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": 1077564, "vin": [ { "gen": { "height": 1077554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f03e4e2ba00f2f3d1a94aff3633261538f4d8dfc39a01145c89bcecf006552a" } } ], "extra": [ 1, 253, 50, 48, 197, 231, 217, 39, 218, 126, 72, 53, 25, 241, 163, 219, 85, 142, 236, 98, 231, 212, 132, 123, 82, 108, 251, 198, 119, 137, 239, 13, 62, 2, 17, 0, 0, 0, 1, 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