Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e75153b00197e4b4a1c8aa522abc57d4e151e9332312dd83826535160a5c182d

Tx prefix hash: f8f7b4a8ee5614cef23603fdc2c9dbba119a8c2b032cd6ce6526c5f5aa095ecb
Tx public key: ffa17b75fcf3174e7285a3b2ae3ab61b413483d1a08b553320a095ef3e0764ba
Timestamp: 1718653496 Timestamp [UCT]: 2024-06-17 19:44:56 Age [y:d:h:m:s]: 00:292:09:33:02
Block: 1046392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208944 RingCT/type: yes/0
Extra: 01ffa17b75fcf3174e7285a3b2ae3ab61b413483d1a08b553320a095ef3e0764ba0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dffa6506bded04d5979bdf21895246b2ba10570bfb16391e8ab116473f1d50e 0.600000000000 1516203 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": 1046402, "vin": [ { "gen": { "height": 1046392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dffa6506bded04d5979bdf21895246b2ba10570bfb16391e8ab116473f1d50e" } } ], "extra": [ 1, 255, 161, 123, 117, 252, 243, 23, 78, 114, 133, 163, 178, 174, 58, 182, 27, 65, 52, 131, 209, 160, 139, 85, 51, 32, 160, 149, 239, 62, 7, 100, 186, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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