Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c99e00321237b45cd40e4c54f121402132140d75fedf1900abb860ac3ee03fd7

Tx prefix hash: 3c9e10f161fadae3f55a16d903af6de5287c0d6d21d499daf701dcf1f4e7ac79
Tx public key: 4829ce130e4e95196bd22b3dd51c68e398ff1a5fc4d63e0ef78ad2860f4e59e2
Timestamp: 1694758375 Timestamp [UCT]: 2023-09-15 06:12:55 Age [y:d:h:m:s]: 01:100:10:35:04
Block: 848476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333118 RingCT/type: yes/0
Extra: 014829ce130e4e95196bd22b3dd51c68e398ff1a5fc4d63e0ef78ad2860f4e59e2021100000018faf35c9c000000000000000000

1 output(s) for total of 0.947647567000 dcy

stealth address amount amount idx
00: b8c50fcd369422abcdb6985288ce09c2dd52d0f15f4dbe9e02cabaf5328fffcb 0.947647567000 1302078 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": 848486, "vin": [ { "gen": { "height": 848476 } } ], "vout": [ { "amount": 947647567, "target": { "key": "b8c50fcd369422abcdb6985288ce09c2dd52d0f15f4dbe9e02cabaf5328fffcb" } } ], "extra": [ 1, 72, 41, 206, 19, 14, 78, 149, 25, 107, 210, 43, 61, 213, 28, 104, 227, 152, 255, 26, 95, 196, 214, 62, 14, 247, 138, 210, 134, 15, 78, 89, 226, 2, 17, 0, 0, 0, 24, 250, 243, 92, 156, 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