Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19b09a53c0862811bcf4bf93c1af87409cd41218daa53b2e23dbc6ad3521eb8d

Tx prefix hash: 385ad4c0b20e10ae1f0c809f7e9549345034b009619fad545a19ad7108296493
Tx public key: fa18bc03b767df6b965a59f160669bc97320eaf423ec2cd29d7e982a95345536
Timestamp: 1581257478 Timestamp [UCT]: 2020-02-09 14:11:18 Age [y:d:h:m:s]: 04:291:21:36:28
Block: 61454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1100645 RingCT/type: yes/0
Extra: 01fa18bc03b767df6b965a59f160669bc97320eaf423ec2cd29d7e982a9534553602110000000e4943cd9f000000000000000000

1 output(s) for total of 384.041540791000 dcy

stealth address amount amount idx
00: 7e5aed7d1d3b1ff6b9305595e708529f617d707ec17f685541b8ea850ab0027e 384.041540791000 113257 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": 61464, "vin": [ { "gen": { "height": 61454 } } ], "vout": [ { "amount": 384041540791, "target": { "key": "7e5aed7d1d3b1ff6b9305595e708529f617d707ec17f685541b8ea850ab0027e" } } ], "extra": [ 1, 250, 24, 188, 3, 183, 103, 223, 107, 150, 90, 89, 241, 96, 102, 155, 201, 115, 32, 234, 244, 35, 236, 44, 210, 157, 126, 152, 42, 149, 52, 85, 54, 2, 17, 0, 0, 0, 14, 73, 67, 205, 159, 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