Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b236cffb59956ec2e2740af9359a5530d07afe37cb6d137d0fbd2856396af01d

Tx prefix hash: 61a8fddb5e4755b5a47638e76af254f61af43a909b0ae87f93b3e6b6a91f1388
Tx public key: 5a4cc27545177e95f5630131ba28bf49b0f8ce806f3b92e4fc47620a73ed46f5
Timestamp: 1577885838 Timestamp [UCT]: 2020-01-01 13:37:18 Age [y:d:h:m:s]: 04:333:06:41:26
Block: 36361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127425 RingCT/type: yes/0
Extra: 015a4cc27545177e95f5630131ba28bf49b0f8ce806f3b92e4fc47620a73ed46f50211000000034943cd9f000000000000000000

1 output(s) for total of 465.081703958000 dcy

stealth address amount amount idx
00: 5fcba4538c2869860c0db3ce7bed8bc6557217f5ffa314fe1dfc1d390ebd9903 465.081703958000 61568 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": 36371, "vin": [ { "gen": { "height": 36361 } } ], "vout": [ { "amount": 465081703958, "target": { "key": "5fcba4538c2869860c0db3ce7bed8bc6557217f5ffa314fe1dfc1d390ebd9903" } } ], "extra": [ 1, 90, 76, 194, 117, 69, 23, 126, 149, 245, 99, 1, 49, 186, 40, 191, 73, 176, 248, 206, 128, 111, 59, 146, 228, 252, 71, 98, 10, 115, 237, 70, 245, 2, 17, 0, 0, 0, 3, 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