Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 156f16f2aee912c7a27805f91584adcc7c43409f5646471c99889db0ce9c7988

Tx prefix hash: 88f9b810bc4770f0a8ae515eff5a956ade05267c03026a341dc14024175cc74c
Tx public key: 646a00ff61121693e40538fdeb10304b2d17c03f2aaa6c13d4335d3ce5d9e722
Timestamp: 1647918100 Timestamp [UCT]: 2022-03-22 03:01:40 Age [y:d:h:m:s]: 02:242:11:56:38
Block: 463668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 692785 RingCT/type: yes/0
Extra: 01646a00ff61121693e40538fdeb10304b2d17c03f2aaa6c13d4335d3ce5d9e722021100000021bf7ee4e7000000000000000000

1 output(s) for total of 17.851540396000 dcy

stealth address amount amount idx
00: b040d0b8cfa59cf5c04a7bde1ccd87ceb84dbb587e064e2ad9ead2230a62f699 17.851540396000 881381 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": 463678, "vin": [ { "gen": { "height": 463668 } } ], "vout": [ { "amount": 17851540396, "target": { "key": "b040d0b8cfa59cf5c04a7bde1ccd87ceb84dbb587e064e2ad9ead2230a62f699" } } ], "extra": [ 1, 100, 106, 0, 255, 97, 18, 22, 147, 228, 5, 56, 253, 235, 16, 48, 75, 45, 23, 192, 63, 42, 170, 108, 19, 212, 51, 93, 60, 229, 217, 231, 34, 2, 17, 0, 0, 0, 33, 191, 126, 228, 231, 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