Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a6614b8068b2c0baec9f2ab38e45d708736cda21b0e0deb84e12ec97b8b1a42

Tx prefix hash: 0b2caf130f616b95c07a899ddba381effdcb9d68c4e1614b07f98699fdec80a0
Tx public key: 6e92a1acdddf67ab162580a702dd287c7d64e8d7dd80e8fdd60e7496ec5fe89a
Timestamp: 1678497467 Timestamp [UCT]: 2023-03-11 01:17:47 Age [y:d:h:m:s]: 02:087:14:18:48
Block: 714381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 584201 RingCT/type: yes/0
Extra: 016e92a1acdddf67ab162580a702dd287c7d64e8d7dd80e8fdd60e7496ec5fe89a0211000000035029cbac000000000000000000

1 output(s) for total of 2.636083031000 dcy

stealth address amount amount idx
00: 33ebee943c43a3ff287e2fff6bf142eca738d4f23e32d4ac1862541275f13a4d 2.636083031000 1158638 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": 714391, "vin": [ { "gen": { "height": 714381 } } ], "vout": [ { "amount": 2636083031, "target": { "key": "33ebee943c43a3ff287e2fff6bf142eca738d4f23e32d4ac1862541275f13a4d" } } ], "extra": [ 1, 110, 146, 161, 172, 221, 223, 103, 171, 22, 37, 128, 167, 2, 221, 40, 124, 125, 100, 232, 215, 221, 128, 232, 253, 214, 14, 116, 150, 236, 95, 232, 154, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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