Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf4c6ffd5f352518b5c03e582ee0c6ae052e7dccf4a3e502a10a929b046d6a95

Tx prefix hash: 5494bcc6e5b0673f4cfbe514d997f54608ace28b484dd846949ff382601542c8
Tx public key: f362750f193bab265ea85df596f85a733a26c8d99f07df5692e264c27a0f43ac
Timestamp: 1577939043 Timestamp [UCT]: 2020-01-02 04:24:03 Age [y:d:h:m:s]: 05:282:08:58:34
Block: 36910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1349278 RingCT/type: yes/0
Extra: 01f362750f193bab265ea85df596f85a733a26c8d99f07df5692e264c27a0f43ac0211000000048a2ee0d9000000000000000000

1 output(s) for total of 463.129771848000 dcy

stealth address amount amount idx
00: 91ba287adabe5fbee577c5b8e6868a63928492e0b41c4cd63a7d0448721bde54 463.129771848000 62576 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": 36920, "vin": [ { "gen": { "height": 36910 } } ], "vout": [ { "amount": 463129771848, "target": { "key": "91ba287adabe5fbee577c5b8e6868a63928492e0b41c4cd63a7d0448721bde54" } } ], "extra": [ 1, 243, 98, 117, 15, 25, 59, 171, 38, 94, 168, 93, 245, 150, 248, 90, 115, 58, 38, 200, 217, 159, 7, 223, 86, 146, 226, 100, 194, 122, 15, 67, 172, 2, 17, 0, 0, 0, 4, 138, 46, 224, 217, 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