Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aec828a9e2ad034db8058de13fa8b4ca916efd17b484eb4568fe3e7b06d0a282

Tx prefix hash: 2eb7b25186d2ee7b217ea846de24723622c6dc7c9008f204024acf1f45a918a4
Tx public key: c68d6220d707d5dc75758e4d5e15e0d93c28cf46ef9b8ee1714ddad362d21ca0
Timestamp: 1576628784 Timestamp [UCT]: 2019-12-18 00:26:24 Age [y:d:h:m:s]: 04:345:22:09:43
Block: 27991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1134430 RingCT/type: yes/0
Extra: 01c68d6220d707d5dc75758e4d5e15e0d93c28cf46ef9b8ee1714ddad362d21ca002110000000dd81c26c0000000000000000000

1 output(s) for total of 495.766895833000 dcy

stealth address amount amount idx
00: b91b4a4f18af0119f68efdf8332d979cf94fb3f2712dc23f732b872f186c5bb1 495.766895833000 46447 of 0

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": 28001, "vin": [ { "gen": { "height": 27991 } } ], "vout": [ { "amount": 495766895833, "target": { "key": "b91b4a4f18af0119f68efdf8332d979cf94fb3f2712dc23f732b872f186c5bb1" } } ], "extra": [ 1, 198, 141, 98, 32, 215, 7, 213, 220, 117, 117, 142, 77, 94, 21, 224, 217, 60, 40, 207, 70, 239, 155, 142, 225, 113, 77, 218, 211, 98, 210, 28, 160, 2, 17, 0, 0, 0, 13, 216, 28, 38, 192, 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