Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a210ecffaac387f1ea2482f0b30b3b9fa1c337fa89f5d70da83604260f53a5c4

Tx prefix hash: b80dcafa5df9933b7a47ddc082342dfecd71c768b149ec2d356908f71667c21e
Tx public key: 72e0436e0c26dd49b83550dfc0f7e95d922d92142744c5ce257af29db1b8b5f5
Timestamp: 1583639130 Timestamp [UCT]: 2020-03-08 03:45:30 Age [y:d:h:m:s]: 04:264:10:52:19
Block: 78492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1083687 RingCT/type: yes/0
Extra: 0172e0436e0c26dd49b83550dfc0f7e95d922d92142744c5ce257af29db1b8b5f50211000000115143fba2000000000000000000

1 output(s) for total of 337.228454801000 dcy

stealth address amount amount idx
00: b81f6faf70a8d6fbf1295fd2e7b5521f8b8ba6ca5e0c82d114a6d70d69cda68e 337.228454801000 143952 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": 78502, "vin": [ { "gen": { "height": 78492 } } ], "vout": [ { "amount": 337228454801, "target": { "key": "b81f6faf70a8d6fbf1295fd2e7b5521f8b8ba6ca5e0c82d114a6d70d69cda68e" } } ], "extra": [ 1, 114, 224, 67, 110, 12, 38, 221, 73, 184, 53, 80, 223, 192, 247, 233, 93, 146, 45, 146, 20, 39, 68, 197, 206, 37, 122, 242, 157, 177, 184, 181, 245, 2, 17, 0, 0, 0, 17, 81, 67, 251, 162, 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