Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbda34e67984c63bf948880781b5c07b70a01ced1b590f12930286312a523abe

Tx prefix hash: 8bb41f0090db268a6b952cc71e5be6bdfcae2f46065ec9ceddf5496a93f6df61
Tx public key: c20a9a3403755ea82ee1ea4f289141eeaf3bded3ff4d468a292e5df272d48881
Timestamp: 1577898442 Timestamp [UCT]: 2020-01-01 17:07:22 Age [y:d:h:m:s]: 05:108:19:15:57
Block: 36463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1227676 RingCT/type: yes/0
Extra: 01c20a9a3403755ea82ee1ea4f289141eeaf3bded3ff4d468a292e5df272d488810211000000314ac5aa02000000000000000000

1 output(s) for total of 464.711903841000 dcy

stealth address amount amount idx
00: fb34b0453527a7307274de5a3812dc5471daae92588f4cc70e8177c2de27d110 464.711903841000 61776 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": 36473, "vin": [ { "gen": { "height": 36463 } } ], "vout": [ { "amount": 464711903841, "target": { "key": "fb34b0453527a7307274de5a3812dc5471daae92588f4cc70e8177c2de27d110" } } ], "extra": [ 1, 194, 10, 154, 52, 3, 117, 94, 168, 46, 225, 234, 79, 40, 145, 65, 238, 175, 59, 222, 211, 255, 77, 70, 138, 41, 46, 93, 242, 114, 212, 136, 129, 2, 17, 0, 0, 0, 49, 74, 197, 170, 2, 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