Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 638fa4155f70bd1c3185b90a7f40040c52d3aabb6874e2ce5c4283a6e8c47fef

Tx prefix hash: e511e0479c7da05ced7a3cb469047fcb76a4ae2c59498b54c3736733488830ab
Tx public key: af7d668e4ab7884c52ea70bfa829262ac53c2c0fef175afc88e221a9e12c404a
Timestamp: 1587528879 Timestamp [UCT]: 2020-04-22 04:14:39 Age [y:d:h:m:s]: 04:251:12:24:36
Block: 94661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1090471 RingCT/type: yes/0
Extra: 01af7d668e4ab7884c52ea70bfa829262ac53c2c0fef175afc88e221a9e12c404a0211000000138a2ee0d9000000000000000000

1 output(s) for total of 298.091491517000 dcy

stealth address amount amount idx
00: 053f3bea51e717f96f2a0a51207eb519c5df9e7a2688dd4fc478fb1e82d7523c 298.091491517000 168485 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": 94671, "vin": [ { "gen": { "height": 94661 } } ], "vout": [ { "amount": 298091491517, "target": { "key": "053f3bea51e717f96f2a0a51207eb519c5df9e7a2688dd4fc478fb1e82d7523c" } } ], "extra": [ 1, 175, 125, 102, 142, 74, 183, 136, 76, 82, 234, 112, 191, 168, 41, 38, 42, 197, 60, 44, 15, 239, 23, 90, 252, 136, 226, 33, 169, 225, 44, 64, 74, 2, 17, 0, 0, 0, 19, 138, 46, 224, 217, 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