Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26dd60df23bc9bdceda040644418171407ff3e6670ce9b15c5aafed3f1b276af

Tx prefix hash: 291ab7f869e1fe828aa2068990287bc3098811b0933f67b66c7e891d0f9efe40
Tx public key: ab9590514854c531744d33cb3e813fd2bfe9580bf597b5c0ed4d50d3a1c334ed
Timestamp: 1702923617 Timestamp [UCT]: 2023-12-18 18:20:17 Age [y:d:h:m:s]: 01:150:08:11:21
Block: 915984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368602 RingCT/type: yes/0
Extra: 01ab9590514854c531744d33cb3e813fd2bfe9580bf597b5c0ed4d50d3a1c334ed02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5aa1ffb28c336211e626bba8a7fe3d99266b6feb89b1591fc392cccf350dabea 0.600000000000 1373418 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": 915994, "vin": [ { "gen": { "height": 915984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5aa1ffb28c336211e626bba8a7fe3d99266b6feb89b1591fc392cccf350dabea" } } ], "extra": [ 1, 171, 149, 144, 81, 72, 84, 197, 49, 116, 77, 51, 203, 62, 129, 63, 210, 191, 233, 88, 11, 245, 151, 181, 192, 237, 77, 80, 211, 161, 195, 52, 237, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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