Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2145081c569a7dedb7234d1d02bb5970ae8fb452fec399da3b1907b20d8dd0b

Tx prefix hash: d291a94249d9178afcd7b96fb387c17303ff8880a7172d8a676e2d36debc6e33
Tx public key: c9bf3ea21c08c2bc17fde33c406511c2563bb2a5f100860be109e9180039416c
Timestamp: 1574142939 Timestamp [UCT]: 2019-11-19 05:55:39 Age [y:d:h:m:s]: 05:348:14:04:05
Block: 12456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1389696 RingCT/type: yes/0
Extra: 01c9bf3ea21c08c2bc17fde33c406511c2563bb2a5f100860be109e9180039416c02110000000366a80d00000000000000000000

1 output(s) for total of 558.121803785000 dcy

stealth address amount amount idx
00: 3f9c1004b04851f105e6b558c1c51b7792dc753b07ce704c2618e0dbd79c31c8 558.121803785000 13764 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": 12466, "vin": [ { "gen": { "height": 12456 } } ], "vout": [ { "amount": 558121803785, "target": { "key": "3f9c1004b04851f105e6b558c1c51b7792dc753b07ce704c2618e0dbd79c31c8" } } ], "extra": [ 1, 201, 191, 62, 162, 28, 8, 194, 188, 23, 253, 227, 60, 64, 101, 17, 194, 86, 59, 178, 165, 241, 0, 134, 11, 225, 9, 233, 24, 0, 57, 65, 108, 2, 17, 0, 0, 0, 3, 102, 168, 13, 0, 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