Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70d5632bcfebd82938b3a0c6fdcba40bf00cf00d7af8502157f0771776bc09ae

Tx prefix hash: 54f3ecfd8d36b40bf3199e33d294afb4efaf640678c8aaf248924c08ec8d804a
Tx public key: e87be4ea313d1b5ff8004cc9a8f62d2f2ca93aa6e0b7c843d989d6758b3fd449
Timestamp: 1711318840 Timestamp [UCT]: 2024-03-24 22:20:40 Age [y:d:h:m:s]: 01:022:17:53:25
Block: 985605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277211 RingCT/type: yes/0
Extra: 01e87be4ea313d1b5ff8004cc9a8f62d2f2ca93aa6e0b7c843d989d6758b3fd4490211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2cccb38f66d76f494421f7d7723dc0e5c4137f4e29cccd50ad47206e4ab37c3 0.600000000000 1445822 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": 985615, "vin": [ { "gen": { "height": 985605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2cccb38f66d76f494421f7d7723dc0e5c4137f4e29cccd50ad47206e4ab37c3" } } ], "extra": [ 1, 232, 123, 228, 234, 49, 61, 27, 95, 248, 0, 76, 201, 168, 246, 45, 47, 44, 169, 58, 166, 224, 183, 200, 67, 217, 137, 214, 117, 139, 63, 212, 73, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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