Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adb27f3087d9a6a74903335421b9385bee6ddcc0a05198fda58fed13014b0adf

Tx prefix hash: 38d158e1f620e008ee2b9beab71f60cfef33bfc7b10e7ed6240aad723e4c4406
Tx public key: 78aedfc8e3301f705bda19acb1606ed5bbb663c5431b9450f16f97984b514311
Timestamp: 1584921075 Timestamp [UCT]: 2020-03-22 23:51:15 Age [y:d:h:m:s]: 05:201:04:35:46
Block: 86822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1299108 RingCT/type: yes/0
Extra: 0178aedfc8e3301f705bda19acb1606ed5bbb663c5431b9450f16f97984b51431102110000001c4ac5aa02000000000000000000

1 output(s) for total of 316.474052825000 dcy

stealth address amount amount idx
00: 354641bfd85dda6aa831f239fd3329889f5b6718a8cdc7ecf41c0b4cd7d19d11 316.474052825000 156634 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": 86832, "vin": [ { "gen": { "height": 86822 } } ], "vout": [ { "amount": 316474052825, "target": { "key": "354641bfd85dda6aa831f239fd3329889f5b6718a8cdc7ecf41c0b4cd7d19d11" } } ], "extra": [ 1, 120, 174, 223, 200, 227, 48, 31, 112, 91, 218, 25, 172, 177, 96, 110, 213, 187, 182, 99, 197, 67, 27, 148, 80, 241, 111, 151, 152, 75, 81, 67, 17, 2, 17, 0, 0, 0, 28, 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